home *** CD-ROM | disk | FTP | other *** search
- Path: dtek.chalmers.se!d1mag
- From: d1mag@dtek.chalmers.se (Christian Magnusson)
- Newsgroups: comp.unix.amiga
- Subject: Re: amiga clock wrong under NetBSD (and Linux)
- Date: 20 Jan 1996 03:52:08 GMT
- Organization: Chalmers University of Technology
- Message-ID: <4dpot8$f9r@nyheter.chalmers.se>
- References: <4ddp6d$5qg@stc06.ctd.ornl.gov> <4dff9t$kqv@rrzs3.uni-regensburg.de> <4dil7u$4ls8@news-s01.ny.us.ibm.net> <4dohkl$li4@news1.shell>
- NNTP-Posting-Host: mis.dtek.chalmers.se
-
- In article <4dohkl$li4@news1.shell>,
- John Darrell Kesling <jkesling@shell.portal.com> wrote:
- >Frederick V. Heitkamp (heitkamp@ibm.net) wrote:
- >>Hubert Feyrer (feyrer@rfhs1012.fh.uni-regensburg.de) wrote:
- >>: charles thomas (thomas@ORNL.GOV) wrote:
- >>: > Just got the prebuilt generic NetBSD 1.1 running on my A3000.
- >>: > The date displays a time that's something like 5
- >>: > hours off, even when I set the timezone correctly. Time is
- >>: > correct when I boot into Amiga O/S.
- >
- >>I've noticed that Amiga Linux 1.2.13pl4 does the same thing. Odd.
- >
- >>Fred Heitkamp
- >
- >When you're running Unix the system clock should be set to GMT.
-
- This is correct..
-
- >The difference between EST and GMT is 5 hours. You should be able
- >to get the time to display the same under both operating systems
- >by lying to unix and telling it your in GMT (TZ=GMT ?).
-
- Have you noticed that it's impossible to get correct date after a
- reboot if you had it set to something in the future before. ?
- I made that misstake before and I had some problem before it got synced
- to the actual time.
- The filesystems has some date saved, and if you reboot it will think
- the batteryclock is incorrect. The test is made in /sys/arch/amiga/dev/clock.c
-
- inittodr() { (pseudo code)
- if(battery_clock < filesystem_clock) { time = filesystem_clock }
- else { time = battery_clock }
- }
-
- The only way for me was to boot it up, set the time with 'date' and then
- let the computer be turned on until the batteryclock was greater than the
- filesystemclock. At my next reboot the date&time was OK.
- Of course I could patch the kernel, but isn't there any other way to get
- rid of this problem ?
-
- I understand there are lots of problem if files have wrong dates, mostly
- system logging, make files etc., but are there any good sollution of it ?
-
- Thanks...
-
- Mag
- --
- | Christian 'Mag' Magnusson Computer Science and Engineering
- | Email: d1mag@dtek.chalmers.se Chalmers University of Technology
- | GSM: +46 (0)705 380580
- | WWW: http://www.dtek.chalmers.se/~d1mag
-